home *** CD-ROM | disk | FTP | other *** search
- Path: news.mcs.net!usenet
- From: mikey@mcs.com (Mike Young)
- Newsgroups: comp.lang.ada,comp.lang.c++
- Subject: Re: some questions re. Ada/GNAT from a C++/GCC user
- Date: 31 Mar 1996 00:50:46 GMT
- Organization: Fen Software, Inc.
- Message-ID: <4jkkt6$fdb@Nntp1.mcs.net>
- References: <wnewmanDoxrCp.DKv@netcom.com> <4je9ju$174r@watnews1.watson.ibm.com> <ROGOFF.96Mar28134118@sccm.Stanford.EDU> <4jhe1v$m0g@dayuc.dayton.saic.com> <315CDCF9.31AF@mcs.com> <315D902C.6F7B@escmail.orl.mmc.com>
- NNTP-Posting-Host: mikey.pr.mcs.net
- Mime-Version: 1.0
- Content-Type: Text/Plain; charset=US-ASCII
- X-Newsreader: WinVN 0.99.6
-
- In article <315D902C.6F7B@escmail.orl.mmc.com>, dennison@escmail.orl.mmc.com
- says...
- >
- >Mike Young wrote:
- >>
- >> Hmmmm. Lacking a language based synch method doesn't mean we always go
- >> straight to the semaphore library. I commonly use thin wrappers to guard
- >> precious resources -- for example: mutexes, semaphores, files,
- >> or database sessions. Local scoping allows precise control of lifetimes,
- >> and ensure release even when exceptions are possible:
- >
- >OK. Now what do you do if you have to port that code to DOS? :-)
-
- ===========
- I believe it would then be time to consider relocation. The code itself,
- however, requires only minor modifications: return successful immediately. The
- concept -- resource guarding in a local scope -- still applies. :)
-
- Mike.
-
-